Systems and methods for reserving a replacement rental vehicle

ABSTRACT

A rental self-service (“RSS”) computer system, including a processor and a memory, is provided. The processor is programmed to: (i) verify that a policyholder is eligible to receive a replacement rental; (ii) transmit a customized link to the eligible policyholder; (iii) receive an access request for access of a rental self-service portal, (iv) retrieve policyholder data using information extracted from the customized link; (v) pre-populate a portion of a searchable interface of the rental self-service portal using the retrieved policyholder data; (vi) cause rental vehicle data to be displayed to enable the policyholder to view available rental options and select a vehicle class; (vii) calculate a policyholder cost for renting a selected vehicle class; and (viii) cause to be displayed on the user device (a) the calculated policyholder cost and (b) an option to confirm the rental reservation.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of and claims priority toU.S. patent application Ser. No. 16/026,489, filed Jul. 3, 2018,entitled “Systems and Methods for Reserving a Replacement RentalVehicle”, the contents and disclosures of which are hereby incorporatedherein by reference in its entirety.

FIELD OF THE DISCLOSURE

The present disclosure relates to reserving a replacement rentalvehicle, and more particularly, to a network-based systems and methodsfor enabling a policyholder of an automobile insurance policy toinitiate a rental vehicle reservation.

BACKGROUND

An automobile insurance policyholder may report a loss of vehicle usewith the policyholder's insurer when his or her vehicle is not drivabledue to damage. For example, vehicle damage may occur due to a vehicularaccident or a hit-and-run accident. Most often, a policyholder needs torent a vehicle while his or her vehicle is being repaired. This mayrequire the policyholder to not only file a claim with their insurer,but also communicate extensively with their claims handler and/orinsurance agents to arrange for a replacement vehicle. Oftentimes,policyholders face long claim handling times and confusion during theclaims process as policyholders are frequently transferred betweendifferent departments. Depending on the circumstances surrounding thereported loss and the policyholder's specific insurance provisions, apolicyholder may experience difficulties while trying to secure a rentalvehicle. Furthermore, the claims process typically takes some time, andrequires extensive communication between the policyholder, the claimshandler, the rental vendor, and the repair facility. There exists a needfor a policyholder who has filed a loss with their insurer to initiate arental reservation process on his or her own without having to gothrough a claims handler.

BRIEF SUMMARY

The present embodiments may relate to systems and methods for reservinga replacement rental vehicle after submission of an initial loss claimsubmission. The system may include a rental self-service (“RSS”)computer system, one or more insurance network computer devices, one ormore rental vendor computer devices, and/or one or more repair facilitycomputer devices. The RSS computer system may be associated with aninsurance network, or may be separate from an insurance network but bein communication with an insurance network.

The RSS computer system may be configured to: (i) retrieve policyholderinsurance data from an insurance provider database using a claimidentifier and a policyholder identifier; (ii) verify that thepolicyholder is eligible to receive an insurance replacement rental byperforming a rules-based eligibility check; (iii) cause to be displayedon a user device associated with the policyholder a searchable interfacethat is configured to enable the policyholder to search for at least onerental vendor location; (iv) receive a selected vehicle class inputtedby the policyholder; (v) calculate a policyholder cost for the selectedvehicle class; (vi) display a cost summary to the policyholder; and(vii) receive, from the policyholder, confirmation of a rentalreservation request.

In one aspect, a rental self-service (“RSS”) computer system includes aprocessor in communication with a memory. The processor is programmedto: (i) verify, in response to an initial loss claim filed by apolicyholder, that the policyholder is eligible to receive an insurancereplacement rental by performing an eligibility check using a claimidentifier associated with the initial loss claim and a policyholderidentifier associated with the policyholder; (ii) in response to thepolicyholder being verified as eligible, transmit, to a user deviceassociated with the policyholder, a customized link including arepresentation of the claim identifier and the policyholder identifier;(iii) in response to selection of the customized link at the userdevice, receive, from the user device, an access request for access of arental self-service portal, the access request identifying thecustomized link selected by the policyholder; (iv) retrieve, from adatabase, using the representation of the claim identifier and thepolicyholder identifier extracted from the customized link identified inthe access request, policyholder data; (v) pre-populate a portion of asearchable interface of the rental self-service portal using theretrieved policyholder data, for display on the user device; (vi) inresponse to receiving rental vehicle search input into the searchableinterface, cause rental vehicle data to be displayed on the user deviceto enable the policyholder to view available rental options and select avehicle class available for rent; (vii) calculate a policyholder costfor renting a selected vehicle class based upon the policyholder dataand a corresponding vehicle rental quote for the selected vehicle class,the policyholder cost including a difference between a covered rentalamount indicated in the retrieved policyholder data and a rental costindicated in the vehicle rental quote; and (viii) cause to be displayedon the user device (a) the calculated policyholder cost and (b) anoption to confirm the rental reservation.

In another aspect, a computer-implemented method for enabling apolicyholder to initiate a replacement rental reservation aftersubmission of an initial loss claim is provided. The method isimplemented on a rental self-service (“RSS”) computing device includingat least one processor in communication with at least one memory device.The method includes: (i) verifying, in response to an initial loss claimfiled by a policyholder, that the policyholder is eligible to receive aninsurance replacement rental by performing an eligibility check using aclaim identifier associated with the initial loss claim and apolicyholder identifier associated with the policyholder; (ii) inresponse to the policyholder being verified as eligible, transmitting,to a user device associated with the policyholder, a customized linkincluding a representation of the claim identifier and the policyholderidentifier; (iii) in response to selection of the customized link at theuser device, receiving, from the user device, an access request foraccess of a rental self-service portal, the access request identifyingthe customized link selected by the policyholder; (iv) retrieving, froma database, using the representation of the claim identifier and thepolicyholder identifier extracted from the customized link identified inthe access request, policyholder data; (v) pre-populating a portion of asearchable interface of the rental self-service portal using theretrieved policyholder data, for display on the user device; (vi) inresponse to receiving rental vehicle search input into the searchableinterface, causing rental vehicle data to be displayed on the userdevice to enable the policyholder to view available rental options andselect a vehicle class available for rent; (vii) calculating apolicyholder cost for renting a selected vehicle class based upon thepolicyholder data and a corresponding vehicle rental quote for theselected vehicle class, the policyholder cost including a differencebetween a covered rental amount indicated in the retrieved policyholderdata and a rental cost indicated in the vehicle rental quote; and (viii)causing to be displayed on the user device (a) the calculatedpolicyholder cost and (b) an option to confirm the rental reservation.

In a further aspect, a non-transitory computer-readable storage mediahaving computer-executable instructions embodied thereon for enabling apolicyholder to initiate a replacement rental reservation is provided.When executed by at least one processor of an RSS computing device, thecomputer-executable instructions cause the at least one processor to:(i) verify, in response to an initial loss claim filed by apolicyholder, that the policyholder is eligible to receive an insurancereplacement rental by performing an eligibility check using a claimidentifier associated with the initial loss claim and a policyholderidentifier associated with the policyholder; (ii) in response to thepolicyholder being verified as eligible, transmit, to a user deviceassociated with the policyholder, a customized link including arepresentation of the claim identifier and the policyholder identifier;(iii) in response to selection of the customized link at the userdevice, receive, from the user device, an access request for access of arental self-service portal, the access request identifying thecustomized link selected by the policyholder; (iv) retrieve, from adatabase, using the representation of the claim identifier and thepolicyholder identifier extracted from the customized link identified inthe access request, policyholder data; (v) pre-populate a portion of asearchable interface of the rental self-service portal using theretrieved policyholder data, for display on the user device; (vi) inresponse to receiving rental vehicle search input into the searchableinterface, cause rental vehicle data to be displayed on the user deviceto enable the policyholder to view available rental options and select avehicle class available for rent; (vii) calculate a policyholder costfor renting a selected vehicle class based upon the policyholder dataand a corresponding vehicle rental quote for the selected vehicle class,the policyholder cost including a difference between a covered rentalamount indicated in the retrieved policyholder data and a rental costindicated in the vehicle rental quote; and (viii) cause to be displayedon the user device (a) the calculated policyholder cost and (b) anoption to confirm the rental reservation.

In one aspect, a rental self-service (“RSS”) computer system configuredto enable a policyholder of an automobile insurance policy to initiatean insurance replacement rental reservation may be provided. In someexemplary embodiments, the RSS computer system may include a processorin communication with a memory. The processor may be programmed to: (i)retrieve, from an insurance provider database, policyholder insurancedata using a claim identifier associated with the initial loss claimsubmission, and a policyholder identifier associated with thepolicyholder, the insurance provider database associated with aninsurance provider providing the automobile insurance policy to thepolicyholder; (ii) verify that the policyholder is eligible to receivean insurance replacement rental by performing an eligibility check usingthe claim identifier and the policyholder identifier, wherein theeligibility check includes applying eligibility rules stored in thememory to determine policyholder eligibility; (iii) cause to bedisplayed on a user device associated with the policyholder a searchableinterface that is prepopulated with at least some of the policyholderinsurance data and linked to a subset of rental vehicle data storedwithin the memory, the searchable interface configured to enable thepolicyholder to search for at least one rental vendor location of atleast one rental vendor applicable to the policyholder; (iv) receive aselected vehicle class inputted by the policyholder via the user device,wherein the selected vehicle class is available for rent at the at leastone rental vendor location; (v) calculate, a policyholder cost for theselected vehicle class based upon the policyholder insurance data, theselected vehicle class, and the rental vehicle data for the at least onerental vendor; (vi) display, to the policyholder, a cost summaryincluding the policyholder cost and information as to the calculation ofthe policyholder cost; and (vii) receive, from the policyholder,confirmation of a rental reservation request of the selected vehicleclass at the at least one rental vendor location. The RSS computersystem may have additional, less, or alternate functionality, includingthat discussed elsewhere herein.

In another aspect, a computer-implemented method for enabling apolicyholder of an automobile insurance policy to initiate an insurancereplacement rental reservation may be provided. The method may beimplemented using a rental self-service (“RSS”) computing device. TheRSS computing device may include at least one processor in communicationwith at least one memory device. The method may include: (i) retrieving,by the RSS computing device, policyholder insurance data from aninsurance provider database using a claim identifier associated with theinitial loss claim submission, and a policyholder identifier associatedwith the policyholder, the insurance provider database associated withan insurance provider providing the automobile insurance policy to thepolicyholder; (ii) verifying that the policyholder is eligible toreceive an insurance replacement rental by performing an eligibilitycheck using the claim identifier and the policyholder identifier,wherein the eligibility check includes applying eligibility rules storedin the memory to determine policyholder eligibility; (iii) causing to bedisplayed on a user device associated with the policyholder a searchableinterface that is prepopulated with at least some of the policyholderinsurance data and linked to a subset of rental vehicle data storedwithin the memory, the searchable interface configured to enable thepolicyholder to search for at least one rental vendor location of atleast one rental vendor applicable to the policyholder; (iv) receiving aselected vehicle class inputted by the policyholder via the user device,wherein the selected vehicle class is available for rent at the at leastone rental vendor location; (v) calculating a policyholder cost for theselected vehicle class based upon the policyholder insurance data, theselected vehicle class, and the rental vehicle data for the at least onerental vendor; (vi) displaying, to the policyholder, a cost summaryincluding the policyholder cost and information as to the calculation ofthe policyholder cost; and (vi) receiving, by the RSS computing devicefrom the policyholder, confirmation of a rental reservation request ofthe selected vehicle class at the at least one rental vendor location.The method may have additional, less, or alternate functionality,including that discussed elsewhere herein.

In at least one further aspect, a non-transitory computer-readablestorage media having computer-executable instructions embodied thereonfor enabling a policyholder of an automobile insurance policy toinitiate an insurance replacement rental reservation may be provided.When executed by at least one processor of an RSS computing device, thecomputer-executable instructions may cause the at least one processorto: (i) retrieve, from an insurance provider database, policyholderinsurance data using a claim identifier associated with the initial lossclaim submission, and a policyholder identifier associated with thepolicyholder, the insurance provider database associated with aninsurance provider providing an automobile insurance policy to thepolicyholder; (ii) verify that the policyholder is eligible to receivean insurance replacement rental by performing an eligibility check usingthe claim identifier and the policyholder identifier, wherein theeligibility check includes applying stored eligibility rules todetermine policyholder eligibility; (iii) cause to be displayed on auser device associated with the policyholder a searchable interface thatis prepopulated with at least some of the policyholder insurance dataand linked to a subset of stored rental vehicle data, the searchableinterface configured to enable the policyholder to search for at leastone rental vendor location of at least one rental vendor applicable tothe policyholder; (iv) receive a selected vehicle class inputted by thepolicyholder via the user device, wherein the selected vehicle class isavailable for rent at the at least one rental vendor location; (v)calculate, a policyholder cost for the selected vehicle class based uponthe policyholder insurance data, the selected vehicle class, and therental vehicle data for the at least one rental vendor; (vi) display, tothe policyholder, a cost summary including the policyholder cost andinformation as to the calculation of the policyholder cost; and (vii)receive, from the policyholder, confirmation of a rental reservationrequest of the selected vehicle class at the at least one rental vendorlocation. The computer-executable instructions may have additional,less, or alternate functionality, including that discussed elsewhereherein.

Advantages will become more apparent to those skilled in the art fromthe following description of the preferred embodiments which have beenshown and described by way of illustration. As will be realized, thepresent embodiments may be capable of other and different embodiments,and their details are capable of modification in various respects.Accordingly, the drawings and description are to be regarded asillustrative in nature and not as restrictive.

BRIEF DESCRIPTION OF THE DRAWINGS

The Figures described below depict various aspects of the systems andmethods disclosed therein. It should be understood that each Figuredepicts an embodiment of a particular aspect of the disclosed systemsand methods, and that each of the Figures is intended to accord with apossible embodiment thereof. Further, wherever possible, the followingdescription refers to the reference numerals included in the followingFigures, in which features depicted in multiple Figures are designatedwith consistent reference numerals.

There are shown in the drawings arrangements which are presentlydiscussed, it being understood, however, that the present embodimentsare not limited to the precise arrangements and are instrumentalitiesshown, wherein:

FIG. 1 illustrates a flow chart of an exemplary process of initiating arental reservation in accordance with one aspect of the presentdisclosure.

FIG. 2 illustrates a flow chart of an exemplary computer-implementedprocess for one aspect of the process of initiating a rental reservationas shown in FIG. 1 , in accordance with one aspect of the presentdisclosure.

FIG. 3 illustrates a simplified block diagram of an exemplary computersystem for implementing the process shown in FIG. 1 .

FIG. 4 illustrates an exemplary configuration of a user computer device,in accordance with one aspect of the present disclosure.

FIG. 5 illustrates an exemplary configuration of a server computerdevice, in accordance with one aspect of the present disclosure.

FIG. 6 illustrates a diagram of components of one or more exemplarycomputing devices that may be used in the system shown in FIG. 4 .

FIGS. 7A and 7B illustrate a plurality of views of an exemplary userinterface for initiating a rental reservation in accordance with theprocess shown in FIG. 1 , using the system shown in FIG. 3 .

The Figures depict preferred embodiments for purposes of illustrationonly. One skilled in the art will readily recognize from the followingdiscussion that alternative embodiments of the systems and methodsillustrated herein may be employed without departing from the principlesof the invention described herein.

DETAILED DESCRIPTION OF THE DRAWINGS

The present embodiments may relate to, inter alia, improved systems andmethods for reserving a rental vehicle. The systems and methodsdescribed herein overcome the deficiencies of other known systems. Inone exemplary embodiment, the process may be performed by a rentalself-service (“RSS”) computing device. In the exemplary embodiment, theRSS computing device may be in communication with a user computer device(e.g., a mobile computer device), an insurance network, one or morerental vendors, and one or more repair facilities.

In the exemplary embodiment, the RSS computing device may retrievepolicyholder insurance data from an insurance network using a claimidentifier associated with an initial loss claim submission, and apolicyholder identifier associated with the policyholder. Morespecifically, the RSS computing device retrieves policyholder insurancedata specific to an automobile insurance policy held by the policyholderwho reports a loss (e.g., files an initial loss claim). In the exemplaryembodiment, the claim identifier may be associated with an initial lossclaim submission (e.g., first notice of loss) filed by the policyholder.The claim identifier may be a claim number generated by the RSScomputing device or another insurance network computing device when thepolicyholder files a first notice of loss (e.g., FNOL). The policyholderidentifier may be a policy number or other policy identifier associatedwith the policyholder. In the exemplary embodiment, the policyholder mayprovide the policyholder identifier when filing the FNOL. Thepolicyholder identifier and the claim identifier may be used to retrievethe policyholder's automobile insurance policy as of the date and timethe claim identifier is generated. In the exemplary embodiment, the RSScomputing device uses the claim identifier and the policyholderidentifier to retrieve the policyholder's rental coverage as of the datethe claim identifier is generated.

In the exemplary embodiment, the RSS computing device may extract thepolicyholder identifier and claim identifier from a customized linkgenerated by the RSS computing device during a pre-eligibility process.In the exemplary embodiment, the RSS computing device may generate andtransmit a customized link to a policyholder who passes apre-eligibility check (e.g., a first check). In the exemplaryembodiment, the pre-eligibility check may be performed using theinformation provided by the policyholder in the FNOL. The customizedlink generated by the RSS computing device provides access to aself-service portal that enables the policyholder to initiate a rentalvehicle reservation. When the policyholder proceeds with theself-service rental process via the customized link, the RSS computingdevice may utilize the claim identifier parameter and the policyholderidentifier parameter of the customized link to retrieve the policyholderinsurance data (e.g., rental coverage) from the insurance network. Insome embodiments, an insurance network computing device in communicationwith the RSS computing device may perform the pre-eligibility checkusing the information provided by the policyholder in the FNOL. In theseembodiments, the insurance network computing device may generate thecustomized link.

In the exemplary embodiment, the RSS computing device retrieves thepolicyholder's rental coverage as of the date of the reported loss, anddisplays this information to the policyholder. The policyholder mayreview the displayed rental coverage. In the exemplary embodiment, dailyrental coverage and total rental coverage may be provided to thepolicyholder. The policyholder may confirm that he or she understandstheir rental coverage and wishes to proceed with the self-service rentalprocess. In the exemplary embodiment, the RSS computing device receivesconfirmation from the policyholder, and subsequently performs aneligibility check (e.g., a second check) to verify that the policyholderremains eligible. The RSS computing device may perform the eligibilitycheck by determining that a pay code (e.g., cause of loss) for theinitial loss claim submission (e.g., FNOL) exists (e.g., is open). Inthe exemplary embodiment, the RSS computing device may communicate withan accounting system of the insurer to verify that a rental pay code isopen for the reported loss. In the exemplary embodiment, the rental paycode enables the insurer to directly make payments to a rental vendor.The RSS computing device may use the claim identifier and thepolicyholder identifier to verify that a pay code is open. In someembodiments, the RSS computing device may also apply a set ofeligibility rules to the information provided by the policyholder in theFNOL. The eligibility rules may be similar to the rules applied by theRSS computing device during the pre-eligibility check.

In the exemplary embodiment, the RSS computing device may provide asearchable interface to the policyholder. More specifically, asearchable interface is provided by the RSS computing device, causingthe searchable interface to be displayed to a policyholder (on apolicyholder computing device) who remains eligible to proceed with theself-service rental process. In the exemplary embodiment, the RSScomputing device enables the policyholder to search for rental vendorlocations. In some embodiments, the RSS computing device may enable thepolicyholder to select a rental vendor from a list of vendors who havepartnered with the insurer. In the exemplary embodiment, the RSScomputing device enables the policyholder to customize the search basedon geographical location, zip code, and address (e.g., repair facilityaddress). In these embodiments, the RSS computing device may display, tothe policyholder, available rental vendor location near a selectedrepair facility. In these embodiments, the RSS computing device mayretrieve, from the insurance network, repair facility informationprovided by the policyholder during the initial loss claim submissionprocess.

In the exemplary embodiment, the RSS computing device receives aselected rental vendor location of a selected rental vendor. The RSScomputing device may further receive, from the policyholder, a selectedvehicle class available for rent at the selected rental vendor location.In the example embodiment, the policyholder may select a vehicle class(e.g., sedan, SUV, truck, van). In some embodiments, the RSS computingdevice may allow the policyholder to select a specific make and/or modelof an available rental vehicle at the selected rental vendor location.In other embodiments, the RSS computing device may prompt thepolicyholder to contact the selected rental vendor location to inquireabout available rental vehicles for a selected vehicle class. In certainembodiments, the policyholder may not select a vehicle class.

In the exemplary embodiment, the RSS computing device may calculate apolicyholder cost (e.g., estimated cost) for a selected vehicle class.The policyholder cost may be an hourly, daily, weekly, and/or monthlyestimated cost for the selected vehicle class. The calculation may bebased upon a comparison of a quoted rental cost and coverage provisionsof the policyholder's automobile insurance policy (e.g., rentalcoverage). The RSS computing device may provide the calculations to thepolicyholder to assist the policyholder in selecting a replacementrental vehicle. For example, a policyholder who has a $50 per day rentalcoverage may select a sedan that costs $21 per day, and costs $8 per dayin taxes and fees. In this example, the RSS computing device may providea summary of the estimated daily cost ($29), and notify the policyholderthat the selected vehicle class is covered under the policyholder'srental coverage. In this example, the policyholder may review a summaryof the policyholder cost (e.g., estimated daily cost) and decide to renta more expensive vehicle covered under the rental policy. In anotherexample, the same policyholder may select a van that costs $35 per dayto rent, costs $10 per day in taxes and fees, and an additional $10 inadditional add-on items selected by the policyholder. The RSS computingdevice may alert the policyholder that the policyholder cost exceeds thepolicyholder's daily rental coverage. In some embodiments, the RSScomputing device may output a rental recommendation (e.g., a best rentaloption) for the policyholder based on the calculations. The policyholdermay utilize the calculations and the rental recommendations to select arental vehicle that is covered under the policyholder's coverage, andmeets the policyholder's rental vehicle needs.

In further embodiments, the RSS computing device may provide, to thepolicyholder, a delivery option. The delivery option may enable thepolicyholder to schedule at least one of a vehicle pick-up at theselected rental vendor location, and a vehicle delivery, by the selectedrental vendor location, to the policyholder. In some embodiments, thepolicyholder may elect to have the rental vehicle delivered to adesignated repair facility. In further embodiments, the RSS computingdevice may recommend vehicle delivery to a designated repair facility.In these embodiments, the policyholder's designated repair facility andrepair facility information may be automatically retrieved from thepolicyholder's claim file.

In the exemplary embodiment, the RSS computing device may receive, fromthe policyholder, confirmation of a rental reservation request for aselected vehicle class at the selected rental vendor location. In otherembodiments, the RSS computing device may additionally receive, from thepolicyholder, confirmation of a vehicle delivery option (e.g., vehiclepick-up or vehicle delivery), scheduling information, and repairfacility information. In some embodiments, the RSS computing device mayreceive confirmation of only a selected rental vendor location. In theseembodiments, the policyholder may not have selected a vehicle class. Infurther embodiments, the RSS computing device may transmit the rentalreservation request and claim information of the policyholder to theselected vendor location.

Subsequent to receiving confirmation, the RSS computing device mayprovide, to the policyholder confirmation information, such as a summaryof the selected rental vendor location, selected vehicle class,scheduling information, and policyholder cost. In the exemplaryembodiment, the RSS computing device may provide, to the policyholder,instructions on how to proceed. In further embodiments, the RSScomputing device may transmit the rental reservation information andclaim information, such as the claim identifier to the selected vendorlocation. In other embodiments, the RSS computing device may update thepolicyholder's claim file to include the rental reservation request. Thepolicyholder's claim file may contain information related to the initialloss claim submission. In further embodiments, the RSS computing devicemay also generate a file note for a claims handler. In theseembodiments, the generated file note may be a message in thepolicyholder's claim file notifying the claims handler of the rentalreservation request.

Exemplary technical effects of the systems, methods, andcomputer-readable media described herein may include, for example: (i)improving efficiency by eliminating the need for an eligiblepolicyholder to reserve a rental vehicle through a claims handler; (ii)improving the claims process by eliminating the need for thepolicyholder to repeatedly provide the same information found in theinitial claim loss; (iii) improving wait time by eliminating excessivehold times, call transfers, and multiple contacts; (iv) reducing thechance for possible confusion and miscommunication by allowing thepolicyholder, instead of the insurer, to initiate rental reservation,and schedule a vehicle pick-up or a vehicle delivery; (v) promotingconvenience by enabling eligible policyholders to reserve a rentalvehicle whenever they want to via a customized link provided by the RSScomputing device; (vi) providing eligible policyholders an alternativemethod to review their rental coverage; (vii) enabling policyholders tobetter understand their rental vehicle options and daily rental costsprior to obtaining a rental vehicle; (viii) providing a rules-basedpre-eligibility check to determine whether a policyholder is eligible toreceive a self-service link to access a self-service portal; (ix)generating a customized link for directing an eligible policyholder to aself-service portal that, without additional input from thepolicyholder, provides rental coverage information as of the date of thereported loss; (x) providing a rules-based eligibility check uponaccessing the self-service portal to verify that a policyholder remainseligible; (xi) automatically retrieving policyholder information (e.g.,rental coverage, initial loss report, designated repair facility) from adatabase to facilitate the rental reservation process; (xii) calculatinga daily rental cost estimate for a policyholder reserving a rentalvehicle through the self-service portal by comparing a policyholder'sdaily rental coverage to quoted rental costs for available rentalvehicles; (xiii) enabling a policyholder who is accessing theself-service portal to select and/or remove add-on items that are notcovered by the policyholder's rental coverage; (xiv) enabling apolicyholder who is accessing the self-service portal to scheduledelivery of a selected rental vehicle to a designated location on aspecific date and time; and (xv) providing a rental vehiclerecommendation based on the policyholder's daily coverage and rentalpreferences to a policyholder accessing the self-service portal.

Exemplary Process for Initiating an Insurance Replacement RentalReservation

FIG. 1 illustrates a flow chart of an exemplary process 100 of enablinga policyholder to initiate an insurance replacement rental reservation,in accordance with the present disclosure. In the exemplary embodiment,process 100 is performed by a computer device associated with aninsurance provider. In other embodiments, process 100 is performed by acomputer device in communication with an insurance provider.

In the exemplary embodiment, a computer device associated with aninsurance provider, such as a rental self-service (“RSS”) computingdevice 310 (shown in FIG. 3 ), enables a policyholder (not shown) of theinsurance provider to report 105 a loss. The policyholder may report 105the loss by filing an initial loss claim. In the exemplary embodiment,the policyholder utilizes a computer device, such as a mobile computerdevice, to report 105 the loss. In some embodiments, the policyholdermay report 105 the loss by calling their automobile insurance providervia a mobile device. In the exemplary embodiment, the policyholder mayutilize an application or website, associated with an insurance providerto report 105 the loss. The loss may be damage to a vehicle due to avehicular accident (e.g., collision) or a hit-and-run. In otherexamples, damage may be due to random chance or Mother Nature, such ashail damage or damage from a falling tree limb.

In the exemplary embodiment, RSS computing device 310 (shown in FIG. 3 )receives, from the policyholder, identification information such as apolicy number, a name of the policyholder (e.g., named insured), orboth. RSS computing device 310 also receives information about the lossfrom the policyholder. This information may include, but is not limitedto, the make and model of the vehicle, the circumstances surroundingdamage, and details concerning the current condition of the vehicle. Thevehicle condition details provided may include, but are not limited to,the extent of damage to the vehicle, and any leaking fluids. In theexemplary embodiment, RSS computing device 310 receives, from thepolicyholder, an indication as to whether the policyholder plans toobtain a rental vehicle. In some embodiments, RSS computing device 310may also receive information as to whether the policyholder plans torepair the vehicle. In these embodiments, the policyholder may provide,to RSS computing device 310, repair facility information of a designatedor selected repair facility he or she plans to have the vehicle repair.

In the exemplary embodiment, RSS computing device 310 is configured todetermine if the policyholder passes 110 a pre-eligibility check. Thepre-eligibility check may be a rules-based check. Rules may be stored ina database, and applied to policyholder information inputted by thepolicyholder (e.g., information provided in the initial loss report)along with the policyholder's profile stored within the database (e.g.,policyholder's automobile insurance policy, accident history, claimshistory). RSS computing device 310 performs a pre-eligibility check(e.g., a first check) to determine if the policyholder is eligible toobtain a rental vehicle under the policyholder's automobile insurancepolicy. RSS computing device 310 may determine eligibility by applying aset of eligibility rules to the information provided by thepolicyholder. RSS computing device 310 may utilize models, algorithms,and/or formulas stored within a database to determine eligibility basedon the specific circumstances surrounding the policyholder's reportedloss. For example, vehicular damage due to the insured's negligence maybe assessed differently than vehicular damage due to hail. Eligibilitymay additionally be based on a variety of factors such as (i) state lawsgoverning the policyholder's automobile insurance provisions, (ii)whether the policyholder has rental reimbursement coverage (e.g., rentalcar coverage), (iii) whether the reported loss is of the type coveredunder the policyholder's rental reimbursement coverage, (iv) whether aspecific provision in the policyholder's insurance policy covers rentalvehicles, (v) whether, in a vehicular accident, the other driver is atfault; and (vi) if in a vehicular accident, whether the at-faultdriver's property damage coverage will pay for the policyholder's rentalvehicle. The policyholder may need to meet one, some, or all of theeligibility rules in order to proceed and reserve a rental vehicle onhis or her own. In some embodiments, the policyholder may immediately benotified of the results of the pre-eligibility check. In otherembodiments, there may be a wait time from when the policyholder reports105 a loss (e.g., files an initial claim loss) to when the policyholderis notified of the results of the pre-eligibility check. In theseembodiments, the wait time may be due to additional information requiredby RSS computing device 310 from the policyholder.

If the policyholder does not pass 110 the pre-eligibility check, thepolicyholder is ineligible to initiate a rental vehicle reservation onhis or her own, and the self-service vehicle rental process comes to anend 115. In the exemplary embodiment, if the policyholder passes 110 thepre-eligibility check, RSS computing device 310 enables the policyholderto proceed 120 to a self-service portal. The self-service portal may bean application, website, or webpage that provides the policyholder withcontinuing steps for placing a replacement rental reservation. In someembodiments, the self-service portal may be a separate application orwebsite from the one utilized by the policyholder to report 105 theloss. In other embodiments, the self-service portal may be the sameapplication or website as the one utilized by the policyholder to report105 the loss. In these embodiments, an ineligible policyholder may bedenied further access of the application or website. In the exemplaryembodiment and in the case where the policyholder passes 110 thepre-eligibility check, RSS computing device 310 causes thepolicyholder's computing device to display and execute the self-serviceportal. As explained below, the policyholder accesses the self-serviceportal by executing a customized link that is generated by the RSScomputing device.

In the exemplary embodiment, RSS computing device 310 generatescustomized links associated with the self-service portal. Eachcustomized link connects a specific policyholder to his or herpolicyholder profile (e.g., information as to the policyholder'sautomobile insurance policy, accident history, claims history) storedwithin a database of RSS computing device 310 such as database 320(shown in FIG. 3 ). When a policyholder who passes 110 thepre-eligibility check accesses the customized link on his or her userdevice, RSS computing device 310 prepopulates policyholder insurancedata on a user device associated with the policyholder. Policyholderinsurance data may include the policyholder's automobile insurancepolicy provisions and claim information (e.g., information associatedwith the policyholder's claim file and initial loss report). RSScomputing device 310 may transmit a message (e.g., e-mail, text) to thepolicyholder that includes the customized link such that thepolicyholder may proceed 120 to the self-service portal at a later time.In some embodiments, RSS computing device 310 may generate and transmitthe customized link to policyholders who pass 110 the pre-eligibilitycheck. For example, the policyholder might not consider obtaining arental vehicle at the time of reporting 105 a loss, but later decidesthat he or she wants to rent a vehicle. In other embodiments, RSScomputing device 310 may transmit a customized link to a policyholderwho has not indicated a desire to obtain a rental vehicle, but plans torepair their vehicle.

In the exemplary embodiment, RSS computing device 310 generates acustomized link for the policyholder such that, when accessed by thepolicyholder, the policyholder's insurance information and claiminformation will automatically populate without input from thepolicyholder. In the exemplary embodiment, the customized link containsa policyholder identifier (e.g., policy number) and a claim identifier(e.g., claim number) associated with the reported 105 loss. RSScomputing device 310 may extract the policyholder identifier and theclaim identifier from the customized link, retrieve the policyholder'sinsurance and claim information from the insurance network using theextracted identifiers, and load the self-service portal.

In the exemplary embodiment, RSS computing device 310 causes theself-service portal to display the policyholder's auto insurance policyinformation. The self-service portal may display the policyholder'scoverage provisions, such as rental reimbursement coverage (e.g., rentalcoverage). In the exemplary embodiment, the policyholder's coverage asof the date and time of the filed claim (e.g., reported 105 loss) areretrieved and displayed. In some embodiments, the self-service portalmay also provide an explanation of the policyholder's rental coverage.In the exemplary embodiment, RSS computing device 310 also causes theself-service portal to provide an explanation of the rental process tothe policyholder. RSS computing device 310 is also configured to enablethe policyholder to confirm that he or she is interested in obtaining arental. In some embodiments, RSS computing device 310 may cause theself-service portal to display a confirmation button (e.g., an “Iunderstand” button). In these embodiments, the policyholder clicks theconfirmation button to confirm that he or she understands the insurancecoverage provisions, and is interested in proceeding with the rentalreservation.

In the exemplary embodiment, RSS computing device 310 is configured todetermine if the policyholder passes 125 another rules-based check(e.g., an eligibility check). RSS computing device 310 performs theeligibility check (e.g., a second rules-based check) to verify that thepolicyholder remains eligible for rental vehicle services under thepolicyholder's automobile insurance policy. For example, thepolicyholder may report 105 a loss and pass 110 the pre-eligibilitycheck, but delay in initiating a rental reservation due to circumstancessurrounding the loss (e.g., extensive communications between thepolicyholder's insurance provider and an at-fault driver's insuranceprovider) or simply due to the policyholder's busy schedule. In anotherexample, a policyholder who had no intentions of obtaining a replacementrental at the time of the pre-eligibility check, may later decide torent a vehicle. Thus, in the above examples, a time period may elapsefrom when the policyholder reports 105 the loss (e.g., files an initialloss claim) to when the policyholder proceeds 120 to the self-serviceportal.

In the exemplary embodiment, RSS computing device 310 performs theeligibility check by determining if a pay code (e.g., cause of loss)associated with the initial loss claim submission (e.g., reported 105loss) exists. RSS computing device 310 may determine if a pay codespecific to rentals and/or vehicle rentals exists (e.g., is open) forthe reported 105 loss. In the exemplary embodiment, a pay code for thereported 105 loss enables the insurer to make a payment directly to arental vendor. RSS computing device 310 may be in communication with aclaims accounting system of the insurer. In some embodiments, RSScomputing device 310 may be in communication with a financial system ofthe insurer to determine if the insurer is authorized to pay the claim(e.g., pay for a rental vehicle). In the exemplary embodiment, RSScomputing device 310 reads the policyholder identifier and claimidentifier parameters from the customized link to retrieve thepolicyholder's automobile insurance policy and the reported loss (e.g.,initial loss claim submission). RSS computing device 310 may utilize theretrieved policyholder and claim information to communicate with otherinsurer computing devices, and determine if a pay code exists for thereported loss. RSS computing device 310 may perform the eligibilitycheck without additional input from the policyholder.

If a pay code for the initial loss claim submission does not exist(e.g., is not open), the insurer is unable to pay for the claim. A paycode may not exist because of changes to the initial loss claimsubmission and/or changes to the policyholder's insurance coverage. Forexample, the initial loss claim submission may be updated to reflect newinformation that disqualifies the policyholder from renting a vehicleunder his or her existing insurance coverage. In some embodiments, if apay code (e.g., cause of loss) associated with a rental vehicle does notexist, RSS computing device 310 may systematically open a pay code forthe reported 105 loss, and request confirmation from a financial systemof the insurer. In these embodiments, if RSS computing device 310receives a response from the financial system confirming that the paycode should be open, RSS computing device 310 may determine that thepolicyholder passes 125 the eligibility check. In these embodiments, ifRSS computing device receives a response from the financial systemdenying the pay code (e.g., pay code should not be open), the RSScomputing device 310 may determine that the policyholder does not pass125 the eligibility check.

In some embodiments, RSS computing device 310 may also apply a set ofeligibility rules in addition to determining if a pay code (e.g., causeof loss) exists. Similar to the pre-eligibility check, RSS computingdevice 310 may utilize models, algorithms, and/or formulas to verifyeligibility based on the information provided in the policyholder'sinitial loss claim submission (e.g., reported 105 loss). The eligibilityrules applied to the initial loss claim submission may include the samerules as the rules used in the pre-eligibility check. In someembodiments, the eligibility rules may be different from the rules usedin the pre-eligibility check. The eligibility rules may be based onfactors including (i) state laws governing the policyholder's automobileinsurance coverage, (ii) whether the policyholder has rentalreimbursement coverage (e.g., rental car coverage), (iii) whether thescope of the policyholder's rental reimbursement coverage has changedsince the pre-eligibility check, (iv) whether the reported loss has beenupdated, and (v) whether the reported loss as of the date of theeligibility check is covered under the policyholder's rentalreimbursement coverage. The policyholder may need to meet one, some, orall of the eligibility rules in order to proceed and reserve a rentalvehicle on his or her own.

In the exemplary embodiment, RSS computing device 310 may generate anerror message 130 if the policyholder does not pass 125 the eligibilitycheck. The error message 130 may be displayed to the policyholder afterhe or she confirms interest in obtaining a rental vehicle. For example,upon clicking a confirmation button (e.g., an “I understand” button),the policyholder may receive an error message 130 that directs thepolicyholder to contact his or her claims handler. At this point, thepolicyholder is ineligible to proceed with making a rental vehiclereservation on his or her own, and the self-service vehicle rentalprocess comes to an end 135.

If RSS computing device 310 determines that the policyholder passes 125the eligibility check, the RSS computing device 310 may provide thepolicyholder the ability to search 140 for rental vendors. RSS computingdevice 310 may provide a list of rental vendors from which thepolicyholder may choose from. The list of rental vendors may be storedwithin a database associated with RSS computing device 310 such asdatabase 320 (shown in FIG. 3 ). Additionally, RSS computing device 310may also enable the policyholder to search for a vendor location. In theexemplary embodiment, RSS computing device 310 provides the policyholderwith search options, including geographical location, zip code, andaddress (e.g., repair facility address), that enable the policyholder tocustomize the search. In some embodiments, RSS computing device 310 mayprovide a primary rental vendor for a designated geographical location.In these embodiments, the policyholder may search for locations of theprimary rental vendor using the search options mentioned above.

In the exemplary embodiment, RSS computing device 310 returns a list ofvendor locations based on the search. The policyholder may select 145 avendor location from the list. RSS computing device 310 may also enablethe policyholder to select 150 a vehicle class (e.g., sedan, SUV, truck,van). In some embodiments, selecting 150 a vehicle class may prompt RSScomputing device 310 to display available rental vehicles for theselected vehicle class at the selected rental vendor location. In theseembodiments, RSS computing device 310 may allow the policyholder toselect a specific make and/or model of a rental vehicle available at theselected rental vendor location. RSS computing device 310 may retrieveavailable rental vehicle information through Application ProgrammingInterface (API) calls to the selected rental vendor and/or the selectedrental vendor locations. The selected rental vendor and/or the selectedrental vendor locations may be similar to rental vendor computingdevices 330 (shown in FIG. 3 ). In other embodiments, selecting 150 avehicle class may prompt RSS computing device 310 to display selectedvendor location information (e.g., phone number). In these embodiments,RSS computing device 310 may instruct the policyholder to call theselected vendor location for information on available rental vehiclesfor the selected vehicle class at the selected vendor location.

In certain embodiments, RSS computing device 310 may enable thepolicyholder to first select 150 a vehicle class, and then subsequentlysearch 140 for rental vendors and/or rental vendor locations that havethe selected vehicle class in stock. In these embodiments, thepolicyholder may search 140 for rental vendors and/or rental vendorlocations carrying the selected vehicle class based on geographicallocation, zip code, and address. For example, RSS computing device 310may return a list of rental vendor locations within the policyholder'sinputted zip code currently have the selected vehicle class in stock.The policyholder may select 145 a rental vendor location based on rentalvehicle availability of the policyholder's selected vehicle class.

In the exemplary embodiment, RSS computing device 310 is configured toenable the policyholder to review 155 a cost (e.g., policyholder cost).RSS computing device 310 may provide, to the policyholder, a quote fromthe selected vendor location, such as an estimated daily cost to rent avehicle. In some embodiments, the quoted rental cost may reflect anestimated cost to rent a selected vehicle class. RSS computing device310 may query computing devices of the selected rental vendor and/or theselected rental vendor location through API calls to retrieve quotes foravailable vehicle classes and for additional features and/or services.In certain embodiments, the policyholder may not have selected a vehicleclass. In these embodiments, RSS computing device 310 may provide, tothe policyholder, quotes for a variety of vehicle classes for thepolicyholder to consider. RSS computing device 310 may also compare thequoted daily rental cost to the policyholder's benefit under theirautomobile insurance policy. In the exemplary embodiment, RSS computingdevice 310 may calculate a policyholder cost based on the comparison,and display the policyholder cost to the policyholder. In someembodiments, the calculation of the policyholder cost may include taxesand fees. For example, a policyholder who has a $25 per day coverage mayselect a sedan that costs $21 per day, but costs $8 per day in taxes andfees. In this example, RSS computing device 310 may calculate andprovide to the policyholder, a policyholder cost of $29 and indicatethat the policyholder cost is over the policyholder's daily coveragelimit. In other embodiments, the calculation may reflect additionalcharges not covered by the policyholder's automobile insurance policy.For example, the policyholder may select add-on items that areout-of-pocket expenses of which the policyholder may or may not be awareof RSS computing device 310 may be configured to provide to thepolicyholder a summary of the policyholder cost that provides details ofout-of-pocket expenses. In some embodiments, RSS computing device 310may be configured to provide a rental vehicle recommendation based onthe policyholder's daily coverage and vehicle class preference. In theseembodiments, the policyholder cost of the recommended rental vehiclecalculated by RSS computing device 310 is within the policyholder'sdaily coverage limit.

In the exemplary embodiment, RSS computing device 310 enables thepolicyholder to schedule 160 vehicle pick-up or vehicle delivery. RSScomputing device 310 may instruct the policyholder to select vehiclepick-up or vehicle delivery. In the exemplary embodiment, RSS computingdevice 310 may further prompt the policyholder to designate a specificdate and time for vehicle pick-up or vehicle delivery. In someembodiments, RSS computing device 310 may provide a list of date andtime options for the policyholder to choose from. In certainembodiments, vehicle delivery may be associated with an additional fee(e.g., delivery fee). In these embodiments, RSS computing device 310 maynotify the policyholder of the additional fee associated with thevehicle delivery service. The policyholder may choose to schedulevehicle delivery to a repair facility. In some embodiments, RSScomputing device 310 may recommend vehicle delivery to a designatedrepair facility. In these embodiments, the policyholder may have alreadyselected the designated repair facility, such as when inputtinginformation about the loss in step 105. In these embodiments, RSScomputing device 310 may be in communication with the designated repairfacility to determine vehicle delivery information such as the date andtime that repairs are supposed to begin. In some embodiments, RSScomputing device 310 may be in communication with the designated repairfacility via API calls.

In the exemplary embodiment, RSS computing device 310 may enable thepolicyholder to confirm 165 the rental. RSS computing device 310 mayenable the policyholder to modify the rental reservation at any point inthe self-service process prior to receiving rental reservationconfirmation from the policyholder. After receiving confirmation, RSScomputing device 310 may provide confirmation information such asselected rental vendor location information (e.g., business address,business hours, contact number), a confirmation number, and instructionson how to proceed. In further embodiments, RSS computing device 310 mayprovide information as to the selected vehicle class, a policyholdercost associated with the selected class, repair facility information,and scheduling information (e.g., vehicle delivery date and timewindow). Subsequent to receiving confirmation from the policyholder, RSScomputing device 310 may transmit the rental reservation information andclaim information, such as the claim identifier to the selected vendorlocation. Once the selected vendor location receives the necessaryinformation from RSS computing device 310, the selected vendor locationmay contact the policyholder to confirm receipt of the rentalreservation request. In some embodiments, RSS computing device 310 mayenable the policyholder to modify (e.g., update) a rental reservationafter the policyholder confirms 165 the rental. In these embodiments,RSS computing device 310 may require the policyholder to confirm 165 theupdated rental reservation. In these embodiments, RSS computing device310 may subsequently transmit the updated rental reservation to theselected vendor location.

Exemplary Computer-Implemented Method for Initiating an InsuranceReplacement Rental Reservation

FIG. 2 illustrates a flow chart of an exemplary computer implementedprocess 200 for one aspect of process 100, namely initiating areplacement rental vehicle reservation as shown in FIG. 1 . Morespecifically, process 200 shows the steps that occur after apolicyholder satisfies 110 the pre-eligibility check (shown in FIG. 1 ),and the customized link has been generated. Process 200 may beimplemented by a computing device, for example rental self-service(“RSS”) computing device 310 (shown in FIG. 3 ). In the exemplaryembodiment, RSS computing device 310 may be in communication with a usercomputer device 305 (shown in FIG. 3 ), such as a mobile computerdevice, an insurance network 325 (shown in FIG. 3 ), and one or morerental vendors 330 (shown in FIG. 3 ).

In the exemplary embodiment, process 200 may include retrieving 205 froman insurance provider database, policyholder insurance data using aclaim identifier and a policyholder identifier. The insurance providerdatabase may be associated with an insurance provider providing theautomobile insurance policy to the policyholder. The policyholderinsurance data may be stored in a database associated with RSS computingdevice 310 such as database 320 (shown in FIG. 3 ). The claim identifiermay be associated with an initial loss claim submission (e.g., firstnotice of loss) filed by the policyholder (step 105, shown in FIG. 1 ).The claim identifier may be a claim number generated by the RSScomputing device 310 or another insurance network 325 computing devicewhen the policyholder reports 105 the claim (shown in FIG. 1 ) by filinga first notice of loss (e.g., FNOL). The policyholder identifier may bea policy number associated with the policyholder. The policyholderidentifier and the claim identifier may be used to retrieve thepolicyholder's automobile insurance policy as of the date and time theclaim identifier is generated. RSS computing device 310 may read theclaim identifier and policyholder identifier parameters from thecustomized link already generated to retrieve policyholder insurancedata associated with the claim and policyholder identifiers. Thecustomized link is generated by RSS computing device 310 or anotherinsurance network 325 computing device, and transmitted to thepolicyholder after the policyholder passes 110 the pre-eligibility check(FIG. 1 ).

Process 200 may also include verifying 210 that the policyholder iseligible to receive an insurance replacement rental by performing aneligibility check (FIG. 1 ). The eligibility check may be performedusing the claim identifier and the policyholder identifier. As mentionedabove, the claim identifier and policyholder identifier may be extractedfrom a customized link sent to the policyholder after passing 110 thepre-eligibility check (FIG. 1 ). The claim identifier and policyholderidentifier may be used to retrieve policyholder insurance data, such asinformation associated with (i) the initial loss claim submission and(ii) the policyholder who reported 105 the loss (FIG. 1 ). Theeligibility check may include applying eligibility rules stored in thememory to determine policyholder eligibility. Additionally oralternatively, the eligibility check may include determining if a paycode (e.g., cause of loss) for the initial loss claim submission hasbeen generated and stored within the memory (e.g., cause of loss isopen). RSS computing device 310 may communicate with an accountingsystem of the insurer to check that a pay code associated with rentalvehicles exists for the reported 105 loss (FIG. 1 ).

In some embodiments, if the pay code does not exist (e.g., is not open),RSS computing device 310 may systematically open a rental pay code forthe reported 105 loss, and query the accounting system of the insurer.In these embodiments, RSS computing device 310 may receive a responsefrom the accounting system approving the systematically opened pay code.Based on the received response, RSS computing device 310 may determinethat the policyholder remains eligible, and complete the verificationprocess. In further embodiments, RSS computing device 310 may performthe eligibility check by applying a set of eligibility rules to theinformation provided in the first notice of loss (e.g., initial lossclaim submission). In these embodiments, RSS computing device 310 mayapply the set of eligibility rules in addition to determining that arental pay code associated with the first notice of loss exists. Theeligibility rules may be the same or similar to the rules applied in thepre-eligibility check.

In addition, process 200 may further include causing 215 to be displayedon a user device associated with the policyholder, a searchableinterface configured to enable the policyholder to search for at leastone rental vendor location applicable to the policyholder. Thesearchable interface may be prepopulated with at least some of thepolicyholder insurance data, and linked to a subset of rental vehicledata stored within the memory. The subset of rental vehicle data may bebased on the policyholder's particular geographical location, zip code,and/or address (e.g., repair facility address, policyholder homeaddress). The subset of rental vehicle data may include data as torental vendors partnered with the policyholder's insurance provider(e.g., vendor locations, addresses, business hours, and phone numbers).The subset of rental vehicle data may also include a subset of vehicleclasses available for rent by the rental vendors partnered with thepolicyholder's insurance provider. The subset of rental vehicle data mayfurther include information specific to a rental vendor location such asrental quotes, available add-on features and services, rentaldelivery/pick-up data, and inventory data (e.g., available vehicleclasses, vehicle model and make). The searchable interface may enablethe policyholder to search for rental vendor locations of a selectedrental vendor. In some embodiments, the searchable interface may enablethe policyholder to search for rental vendors partnered with thepolicyholder's insurer. In other embodiments, a rental vendor may bedesignated for the policyholder's particular geographical location. Thesearchable interface may provide filtering features that enable thepolicyholder to search for rental vendor locations based on a zip codeand/or address. Process 200 may further include receiving 220, from thepolicyholder, a selected vehicle class available inputted by thepolicyholder via a user device of the policyholder. The selected vehicleclass may be available for rent at a selected rental vendor location.Subsequent to receiving a selected rental vendor location from thepolicyholder, RSS computing device 310 may enable the policyholder toselect a vehicle class (e.g., sedan, van, truck, minivan). In someembodiments, RSS computing device 310 may enable the policyholder toselect a vehicle make and model. In further embodiments, RSS computingdevice 310 may provide information as to available rental vehicles atthe selected rental vendor location. The available rental vehicleinformation provided to the policyholder may be based on a selectedvehicle class. In other embodiments, RSS computing device 310 mayprovide limited information on rental vehicle availability at theselected vendor location. In these embodiments, RSS computing device 310may provide contact information (e.g., phone number, email) of theselected vendor location, and instruct the policyholder to directlyinquire the selected vendor location as to availabilities. Additionallyor alternatively, RSS computing device 310 may prompt the selectedvendor location to contact the policyholder and provide directinformation as to rental vehicle availability.

Process 200 may also include calculating 225 a policyholder cost to thepolicyholder for the selected vehicle class. The policyholder cost maybe based upon the policyholder insurance data, the selected vehicleclass, and the rental vehicle data for a selected rental vendor. Thepolicyholder cost may be based upon a comparison of a quoted rental costby the selected rental vendor, and coverage provisions of thepolicyholder's automobile insurance policy. Subsequent to receiving aselected vehicle class, RSS computing device 310 may query the selectedvendor location of the selected rental vendor, requesting a rental quotefor the selected vehicle class. In some embodiments, RSS computingdevice 310 may query the selected vendor location and/or the selectedrental vendor through API calls. RSS computing device 310 may receiveand display the rental quote to the policyholder. The rental quote maybe provided to the policyholder as a daily rental quote. RSS computingdevice 310 may additionally compare the received rental quote to thepolicyholder's benefits under their automobile insurance policy, andcalculate the policyholder cost.

Process 200 may also include displaying 230 to the policyholder a costsummary including the policyholder cost and information as to thecalculation of the policyholder cost. The policyholder cost may be basedon factors such as the policyholder's daily coverage limit, the rentalquote received from the selected vendor location, the policyholder'srental period (e.g., hourly, daily, weekly, monthly), fees associatedwith the rental vendor (e.g., delivery fee), and additional add-on itemsthe policyholder has selected. The cost summary may include a list ofthe estimated daily charges such as a daily rental cost quoted by theselected vendor location, taxes and fees, out-of-pocket expenses, andthe daily coverage limit under the policyholder's insurance policy. RSScomputing device 310 may also indicate whether or not the selectedvehicle class is covered under the policyholder's insurance policy, andprovide recommendations based on at least the policyholder's insurancecoverage.

In some embodiments, policyholder may not select a vehicle class. Inthese embodiments, RSS computing device 310 may query the selectedrental vendor location, requesting a daily rental quote for some or allof their available vehicle classes. RSS computing device 310 may receivethis information from the selected rental vendor location, and display,to the policyholder, daily rental quotes for a range of vehicle classes.In this embodiment, RSS computing device 310 may compare the dailyrental quote provided for each of the vehicle classes to thepolicyholder's insurance coverage. RSS computing device 310 may use thecomparisons to calculate a policyholder cost for each of the vehicleclasses it has a daily rental quote for. RSS computing device 310 mayprovide to the policyholder a cost summary of the calculations for eachof the vehicle classes to assist in selecting a rental vehicle.

Process 200 may also include receiving 235, from the policyholder,confirmation of a rental reservation request of the selected vehicleclass at the selected rental vendor location. In some embodiments, thepolicyholder may not have selected a vehicle class. In theseembodiments, RSS computing device 310 may receive 235, from thepolicyholder, a confirmation of a rental reservation request at theselected rental vendor location. Subsequent to receiving 235confirmation from the policyholder, RSS computing device 310 maytransmit the rental reservation request and policyholder information tothe selected rental vendor location. The transmitted rental reservationrequest may include information such as, but not limited to, a selectedvehicle class, a method of retrieving the rental vehicle (e.g., vehiclepick-up or vehicle delivery), scheduling information (e.g., date, time,and location of vehicle pick-up or vehicle delivery), and the length oftime the rental is needed for. The transmitted policyholder informationmay include information such as, but not limited to, the policyholder'spolicy number, the policyholder's insurance coverage (e.g., rentalcoverage), the claim identifier associated with the initial loss claim(e.g., first notice of loss), and a designated repair facility.Subsequent to receiving 235 confirmation, RSS computing device 310 mayprovide the policyholder a confirmation number and instruct thepolicyholder to wait for the selected rental vendor location to contactthe policyholder.

Exemplary Computer Network

FIG. 3 depicts a simplified block diagram of an exemplary computersystem 300 for implementing process 100 shown in FIG. 1 . In theexemplary embodiment, computer system 300 may be used for enabling apolicyholder of an automobile insurance policy to initiate an insurancereplacement rental reservation. As described below in more detail, arental self-service (“RSS”) computing device 310 may be configured to(i) retrieve, from an insurance provider database, policyholderinsurance data using a claim identifier associated with an initial lossclaim submission, and a policyholder identifier associated with thepolicyholder, the insurance provider database associated with aninsurance provider providing the automobile insurance policy to thepolicyholder; (ii) verify that the policyholder is eligible to receivean insurance replacement rental by performing an eligibility check usingthe claim identifier and the policyholder identifier, wherein theeligibility check includes applying eligibility rules stored in thememory to determine policyholder eligibility; (iii) cause to bedisplayed on a user device associated with the policyholder a searchableinterface that is prepopulated with at least some of the policyholderinsurance data and linked to a subset of rental vehicle data storedwithin the memory, the searchable interface configured to enable thepolicyholder to search for at least one rental vendor location of atleast one rental vendor applicable to the policyholder; (iv) receive aselected vehicle class inputted by the policyholder via the user device,wherein the selected vehicle class is available for rent at the at leastone rental vendor location; (v) calculate, a policyholder cost for theselected vehicle class based upon the policyholder insurance data, theselected vehicle class, and the rental vehicle data for the at least onerental vendor; (vi) display, to the policyholder, a cost summaryincluding the policyholder cost and information as to the calculation ofthe policyholder cost; and/or (vii) receive, from the policyholder,confirmation of a rental reservation request of the selected vehicleclass at the at least one rental vendor location.

In the exemplary embodiment, user computer devices 305 are computersthat include a web browser or a software application, which enables usercomputer devices 305 to access remote computer devices, such as RSScomputing device 310 and insurance network computer devices 325, usingthe Internet or other network. More specifically, user computer devices305 may be communicatively coupled to the Internet through manyinterfaces including, but not limited to, at least one of a network,such as the Internet, a local area network (LAN), a wide area network(WAN), or an integrated services digital network (ISDN), adial-up-connection, a digital subscriber line (DSL), a cellular phoneconnection, and a cable modem. User computer devices 305 may be anydevice capable of accessing the Internet including, but not limited to,a desktop computer, a laptop computer, a personal digital assistant(PDA), a cellular phone, a smartphone, a tablet, a phablet, wearableelectronics, smart watch, or other web-based connectable equipment ormobile devices.

A database server 315 may be communicatively coupled to a database 320that stores data. In one embodiment, database 320 may include theeligibility rules, daily cost estimates, rental reservation request,rental vendor information, and repair facility information. In theexemplary embodiment, database 320 may be stored remotely from RSScomputing device 310. In some embodiments, database 320 may bedecentralized. In the exemplary embodiment, the policyholder may accessdatabase 320 via user computer device 305 by logging onto RSS computingdevice 310, as described herein.

RSS computing device 310 may be communicatively coupled with one or moreuser computer devices 305. In some embodiments, RSS computing device 310may be associated with, or is part of a computer network associated withan insurance provider, or in communication with insurance networkcomputer devices 325. In other embodiments, RSS computing device 310 maybe associated with a third party and is merely in communication with theinsurance network computer devices 325. More specifically, RSS computingdevice 310 is communicatively coupled to the Internet through manyinterfaces including, but not limited to, at least one of a network,such as the Internet, a local area network (LAN), a wide area network(WAN), or an integrated services digital network (ISDN), adial-up-connection, a digital subscriber line (DSL), a cellular phoneconnection, and a cable modem.

RSS computing device 310 may perform all of the steps of process 100shown in FIG. 1 . In some embodiments, insurance network computerdevices 325 may be configured to receive an initial loss claimsubmission (e.g., policyholder reports 105 loss) and/or determinewhether a policyholder passes 110 a pre-eligibility check (both shown inFIG. 1 ). In these embodiments, insurance network computer devices 325may be communicatively coupled with RSS computing device 310 to provideclaim information and pre-eligibility check information to RSS computingdevice 310.

RSS computing device 310 may be any device capable of accessing theInternet including, but not limited to, a desktop computer, a laptopcomputer, a personal digital assistant (PDA), a cellular phone, asmartphone, a tablet, a phablet, wearable electronics, smart watch, orother web-based connectable equipment or mobile devices. In theexemplary embodiment, RSS computing device 310 hosts an application orwebsite that allows the policyholder to access the functionalitydescribed herein. In some further embodiments, user computer device 305includes an application that facilitates communication with RSScomputing device 310. RSS computing device 310 is capable ofcommunicating with insurance network computer devices 325, rental vendorcomputer devices 330, and repair facility computer devices 335 throughan application programming interface (API). RSS computing device 310 mayalso use APIs to communicate with outside applications, such as, but notlimited to, data sources about the damaged vehicle, data sources aboutdriver information concerning the policyholder, access to lawenforcement and/or state laws governing automobile insurance policiesand rental vehicles, and other applications as necessary.

In the exemplary embodiment, insurance network computer devices 325include one or more computer devices associated with an insuranceprovider. In the exemplary embodiment, insurance provider is associatedwith the policyholder and the policyholder has an automobile insurancepolicy that insures his or her vehicle with insurance provider. In theexemplary embodiment, insurance network computer devices 325 include aweb browser or a software application, which enables insurance networkcomputer devices 325 to access remote computer devices, such as RSScomputing device 310 and database server 315, using the Internet orother network. More specifically, insurance network computer devices 325may be communicatively coupled to the Internet through many interfacesincluding, but not limited to, at least one of a network, such as theInternet, a local area network (LAN), a wide area network (WAN), or anintegrated services digital network (ISDN), a dial-up-connection, adigital subscriber line (DSL), a cellular phone connection, and a cablemodem. Insurance network computer devices 325 may be any device capableof accessing the Internet including, but not limited to, a desktopcomputer, a laptop computer, a personal digital assistant (PDA), acellular phone, a smartphone, a tablet, a phablet, wearable electronics,smart watch, or other web-based connectable equipment or mobile devices.In some embodiments, insurance network computer devices 325 may accessdatabase 320 to update eligibility rules, review daily rental estimates,and/or review rental reservation requests.

In the exemplary embodiment, rental vendor computer devices 330 includecomputer devices associated with rental vendors capable of providingrental vehicles. More specifically, rental vendor computer devices 330may provide rental vendor information such as available locations (e.g.,branches) of a rental vendor. In the exemplary embodiment, rental vendorcomputer devices 330 include a web browser or a software application,which enables rental vendor computer devices 330 to access remotecomputer devices, such as RSS computing device 310, using the Internetor other network. More specifically, rental vendor computer devices 330may be communicatively coupled to the Internet through many interfacesincluding, but not limited to, at least one of a network, such as theInternet, a local area network (LAN), a wide area network (WAN), or anintegrated services digital network (ISDN), a dial-up-connection, adigital subscriber line (DSL), a cellular phone connection, and a cablemodem. Rental vendor computer devices 330 may be any device capable ofaccessing the Internet including, but not limited to, a desktopcomputer, a laptop computer, a personal digital assistant (PDA), acellular phone, a smartphone, a tablet, a phablet, wearable electronics,smart watch, or other web-based connectable equipment or mobile devices.Rental vendor computer devices 330 may also include computer devicesassociated with a selected rental vendor and a selected rental vendorlocation. Rental vendor computing devices 330 may communicate with RSScomputing device 310 during the rental reservation process and provideinformation such as rental quotes (e.g., hourly, daily, weekly, and/ormonthly rental quotes) for vehicle classes, and available vehicleclasses for rent. Rental vendor computer devices 330 may communicatewith database 320 to retrieve information about the policyholder,information about the loss report, and information related to the rentalreservation request.

In the exemplary embodiment, repair facility computer devices 333include computer devices associated with repair facilities capable ofrepairing object. In the exemplary embodiment, repair facility computerdevices 335 include a web browser or a software application, whichenables repair facility computer devices 335 to access remote computerdevices, such as RSS computing device 310, using the Internet or othernetwork. More specifically, repair facility computer devices 335 may becommunicatively coupled to the Internet through many interfacesincluding, but not limited to, at least one of a network, such as theInternet, a local area network (LAN), a wide area network (WAN), or anintegrated services digital network (ISDN), a dial-up-connection, adigital subscriber line (DSL), a cellular phone connection, and a cablemodem. Repair facility computer devices 335 may be any device capable ofaccessing the Internet including, but not limited to, a desktopcomputer, a laptop computer, a personal digital assistant (PDA), acellular phone, a smartphone, a tablet, a phablet, wearable electronics,smart watch, or other web-based connectable equipment or mobile devices.In some embodiments, repair facility computer devices 335 maycommunicate with RSS computing device 310 to schedule delivery of therental vehicle to the repair facility. Repair facility computer devices335 may provide RSS computing device 310 with scheduling informationsuch as the date and time repairs will begin. In other embodiments,repair facility computer devices 335 may communicate with database 320to retrieve information about the loss report. In these embodiments, thepolicyholder plans to have his or her vehicle repaired at a designated(e.g., selected) repair facility.

Exemplary Client Device

FIG. 4 depicts an exemplary configuration 400 of user computer device402, in accordance with one embodiment of the present disclosure. In theexemplary embodiment, user computer device 402 may be similar to, or thesame as, user computer device 305 (shown in FIG. 3 ). User computerdevice 402 may be operated by a user 401. User computer device 402 mayinclude, but is not limited to, user computer devices 305, insurancenetwork computer devices 325, rental vendor computer devices 330, andrepair facility computer devices 335 (all shown in FIG. 3 ). Usercomputer device 402 may include a processor 405 for executinginstructions. In some embodiments, executable instructions may be storedin a memory area 410. Processor 405 may include one or more processingunits (e.g., in a multi-core configuration). Memory area 410 may be anydevice allowing information such as executable instructions and/ortransaction data to be stored and retrieved. Memory area 410 may includeone or more computer readable media.

User computer device 402 may also include at least one media outputcomponent 415 for presenting information to user 401. Media outputcomponent 415 may be any component capable of conveying information touser 401. In some embodiments, media output component 415 may include anoutput adapter (not shown) such as a video adapter and/or an audioadapter. An output adapter may be operatively coupled to processor 405and operatively coupleable to an output device such as a display device(e.g., a cathode ray tube (CRT), liquid crystal display (LCD), lightemitting diode (LED) display, or “electronic ink” display) or an audiooutput device (e.g., a speaker or headphones).

In some embodiments, media output component 415 may be configured topresent a graphical user interface (e.g., a web browser and/or a clientapplication) to user 401. A graphical user interface may include, forexample, an interface for viewing rental vendor search results, selectedrental vendor location information, daily estimate costs, and otherrental reservation information. In some embodiments, user computerdevice 402 may include an input device 420 for receiving input from user401. User 401 may use input device 420 to, without limitation, selectand/or enter one or more items of information about rental vendorlocation, vehicle class, and/or rental delivery preferences.

Input device 420 may include, for example, a keyboard, a pointingdevice, a mouse, a stylus, a touch sensitive panel (e.g., a touch pad ora touch screen), a gyroscope, an accelerometer, a position detector, abiometric input device, and/or an audio input device. A single componentsuch as a touch screen may function as both an output device of mediaoutput component 415 and input device 420.

User computer device 402 may also include a communication interface 425,communicatively coupled to a remote device such as RSS computing device310 (shown in FIG. 3 ). Communication interface 425 may include, forexample, a wired or wireless network adapter and/or a wireless datatransceiver for use with a mobile telecommunications network.

Stored in memory area 410 are, for example, computer readableinstructions for providing a user interface to user 401 via media outputcomponent 415 and, optionally, receiving and processing input from inputdevice 420. A user interface may include, among other possibilities, aweb browser and/or a client application. Web browsers enable users, suchas user 401, to display and interact with media and other informationtypically embedded on a web page or a website from RSS computing device310. A client application may allow user 401 to interact with, forexample, RSS computing device 310. For example, instructions may bestored by a cloud service, and the output of the execution of theinstructions sent to the media output component 415.

Exemplary Server Device

FIG. 5 depicts an exemplary configuration 500 of a server computerdevice 501, in accordance with one embodiment of the present disclosure.In the exemplary embodiment, server computer device 501 may be similarto, or the same as, RSS computing device 310 (shown in FIG. 3 ). Servercomputer device 501 may include, but is not limited to, RSS computingdevice 310, insurance network computer devices 325, rental vendorcomputer device 330, repair facility computer device 335, and databaseserver 315 (all shown in FIG. 3 ). Server computer device 501 may alsoinclude a processor 505 for executing instructions. Instructions may bestored in a memory area 510. Processor 505 may include one or moreprocessing units (e.g., in a multi-core configuration).

Processor 505 may be operatively coupled to a communication interface515 such that server computer device 501 is capable of communicatingwith a remote device such as another server computer device 501, RSScomputing device 310, insurance network computer devices 325, rentalvendor computer device 330, repair facility computer device 335, anduser computer devices 305 (all shown in FIG. 3 ) (for example, usingwireless communication or data transmission over one or more radio linksor digital communication channels). For example, communication interface515 may receive requests from user computer devices 305 via theInternet, as illustrated in FIG. 3 .

Processor 505 may also be operatively coupled to a storage device 534.Storage device 534 may be any computer-operated hardware suitable forstoring and/or retrieving data, such as, but not limited to, dataassociated with database 320 (shown in FIG. 3 ). In some embodiments,storage device 534 may be integrated in server computer device 501. Forexample, server computer device 501 may include one or more hard diskdrives as storage device 534.

In other embodiments, storage device 534 may be external to servercomputer device 501 and may be accessed by a plurality of servercomputer devices 501. For example, storage device 534 may include astorage area network (SAN), a network attached storage (NAS) system,and/or multiple storage units such as hard disks and/or solid statedisks in a redundant array of inexpensive disks (RAID) configuration.

In some embodiments, processor 505 may be operatively coupled to storagedevice 534 via a storage interface 520. Storage interface 520 may be anycomponent capable of providing processor 505 with access to storagedevice 534. Storage interface 520 may include, for example, an AdvancedTechnology Attachment (ATA) adapter, a Serial ATA (SATA) adapter, aSmall Computer System Interface (SCSI) adapter, a RAID controller, a SANadapter, a network adapter, and/or any component providing processor 505with access to storage device 534.

Processor 505 may execute computer-executable instructions forimplementing aspects of the disclosure. In some embodiments, theprocessor 505 may be transformed into a special purpose microprocessorby executing computer-executable instructions or by otherwise beingprogrammed. For example, the processor 505 may be programmed with theinstruction such as illustrated in FIG. 2 .

Exemplary Computer Device

FIG. 6 depicts a diagram 600 of components of one or more exemplarycomputing devices 610 that may be used in system 300 shown in FIG. 3 .In some embodiments, computing device 610 may be similar to RSScomputing device 310. Database 620 may be coupled with several separatecomponents within computing device 610, which perform specific tasks. Inthis embodiment, database 620 may include the eligibility rules 622,daily cost estimates 624, rental reservation request 626, and rentalvendor information 628. In some embodiments, database 620 is similar todatabase 320 (shown in FIG. 3 ).

Computing device 610 may include the database 620, as well as datastorage devices 630. Computing device 610 may also include a retrievingcomponent 640 for retrieving 205 policyholder insurance data from aninsurance provider database using a claim identifier and a policyholderidentifier (shown in FIG. 2 ). Computing device 610 may also include averifying component 650 for verifying 210 that the policyholder iseligible to receive an insurance replacement rental by performing aneligibility check using the claim identifier and the policyholderidentifier (shown in FIG. 2 ). Computing device 610 may further includea communication component 660 for causing 215 to be displayed on a userdevice associated with the policyholder a searchable interfaceconfigured to enable the policyholder to search for at least one rentalvendor location, receiving 220 a selected vehicle class inputted by thepolicyholder, displaying 230 a cost summary including the policyholdercost and information as to the calculation of the policyholder cost, andreceiving 235 a confirmation of a rental reservation request from thepolicyholder (all shown in FIG. 2 ). Moreover, computing device 610 mayinclude a calculating component 670 for calculating 225 a policyholdercost for a selected vehicle class (shown in FIG. 2 ). A processingcomponent 680 may assist with execution of computer-executableinstructions associated with the system.

Exemplary User Interface

FIGS. 7A and 7B illustrate a plurality of views or screenshots of a userinterface 700 for initiating a rental vehicle reservation using system300 (shown in FIG. 3 ). In the exemplary embodiment, user interface 700is displayed on user computer device 305 (shown in FIG. 3 ).

A first view 705 (e.g., rental coverage view) of user interface 700contains the insurance coverage provisions of the policyholder. As shownin first view 705, an explanation of the policyholder's rental coverageis provided to the policyholder. In this embodiment, first view 705displays the daily rental coverage amount and the total rental coverageamount. In this view, a brief explanation of when coverage may start isprovided for non-drivable vehicles and for drivable vehicles. In thisembodiment, first view 705 notifies the policyholder that additionaloptions offered by the rental vendor are not part of the rental coverage(e.g., out-of-pocket expenses). In the exemplary embodiment, thepolicyholder presses a confirmation button such as an “I understand”button after reviewing his or her coverages. By pressing theconfirmation button, the policyholder indicates that he or she remainsinterested in placing a rental vehicle reservation request.

A second view 710 (e.g., find a vendor view) illustrates what occursafter the policyholder presses the confirmation button to begin theprocess. Specifically, second view 710 illustrates what occurs after thepolicyholder passes 125 the eligibility check (shown in FIG. 1 ). Asshown in second view 710, the policyholder may search for vendorlocations. In some embodiments, second view 710 may instruct thepolicyholder to select a vendor before searching for vendor locations.In these embodiments, second view 710 may provide a list of rentalvendors that are partnered with the policyholder's insurer. In certainembodiments, second view 710 may enable the policyholder to search forand select a specific rental vendor. In the exemplary embodiment, secondview 710 provides a search interface that enables the policyholder tosearch by city and state. In further embodiments, the search interfacemay automatically populate the policyholder's city and state. In theexemplary embodiment, second view 710 provides, to the policyholder, anexplanation of what to expect after selecting a rental vendor location.Second view 710 notifies the policyholder that after choosing a vendorlocation, the policyholder's information is sent to the vendor. Secondview 710 further explains to the policyholder that the rental vendor(e.g., rental vendor location) will contact the policyholder to confirmthe rental vehicle reservation.

A third view 715 (e.g., select a vendor location view) illustrates whatoccurs after the policyholder searches for a vendor location based oncity and state. The policyholder may also search for vendor locations byinputting a specific address, such as a repair facility address. Thirdview 715 provides search results of rental vendor locations within thepolicyholder's city. Third view 715 may provide the search results as alist, and may display the nearest rental vendor location (in referenceto the inputted city and/or state) first and the farthest rental vendorlocation last. In some embodiments, third view 715 may display rentalvendor locations near a designated repair facility without thepolicyholder having to input the repair facility address. In theseembodiments, the policyholder may have provided repair facilityinformation to RSS computing device 310 (shown in FIG. 3 ) in theinitial claim loss submission (e.g., first notice of loss). In theexemplary embodiment, third view 715 provides a button, such as a “renthere” button, that allows the policyholder to select a displayed rentalvendor location. As shown in third view 815, vendor location informationsuch as business address may be provided to the policyholder.

A fourth view 720 (e.g., rental confirmation view) illustrates whatoccurs when the policyholder selects a rental vendor location.Specifically, fourth view 720 prompts the policyholder to confirm theselected rental location. Fourth view 720 provides the policyholder anoption to cancel and confirm. In some embodiments, fourth view 720 mayprompt the policyholder to confirm additional information such as aselected vehicle class, a vehicle delivery method (e.g., vehiclepick-up, vehicle delivery), and a corresponding date and time forvehicle delivery. In further embodiments, fourth view 720 may alsoprovide a policyholder cost for a selected rental vehicle class. Inthese embodiments, fourth view 720 may prompt the policyholder toconfirm that he or she understands the rental charges. For example, thepolicyholder may have selected a vehicle class and additional add-onitems that have a policyholder cost that is over the daily coveragelimit set by the policyholder's rental coverage. In these embodiments,fourth view 720 may explain the out-of-pocket expenses, and require thepolicyholder press a button confirming he or she understands.

A fifth view 725 (e.g., confirmed rental view) illustrates what occurswhen the policyholder confirms the rental reservation request. Fourthview 725 provides the policyholder with information as to what thepolicyholder may expect next. Fourth view 725 displays contactinformation for the selected rental vendor location, such as an address,phone number, business hours, and a selected rental vendor website. Inthe exemplary embodiment, fourth view 725 notifies the policyholder thatthe selected rental vendor will receive the rental reservation requestas well as policyholder information. Fourth view 725 may further notifythe policyholder that his or her claim file may be updated to reflectthe rental reservation request information. In the exemplary embodiment,fourth view 725 enables the policyholder to return to a user homepage,such as a dashboard.

Exemplary Embodiments & Functionality

In one aspect, a computer system for reserving a rental vehicle may beprovided. The computer system may enable a policyholder of an automobileinsurance policy to initiate an insurance replacement rental subsequentto an initial loss claim submission. The computer system may include aprocessor in communication with a memory. The processor may beconfigured or programmed to: (1) retrieve, from an insurance providerdatabase, policyholder insurance data using a claim identifierassociated with the initial loss claim submission, and a policyholderidentifier associated with the policyholder, the insurance providerdatabase associated with an insurance provider providing the automobileinsurance policy to the policyholder; (2) verify that the policyholderis eligible to receive an insurance replacement rental by performing aneligibility check using the claim identifier and the policyholderidentifier, wherein the eligibility check includes applying eligibilityrules stored in the memory to determine policyholder eligibility; (3)cause to be displayed on a user device associated with the policyholdera searchable interface that is prepopulated with at least some of thepolicyholder insurance data and linked to a subset of rental vehicledata stored within the memory, the searchable interface configured toenable the policyholder to search for at least one rental vendorlocation of at least one rental vendor applicable to the policyholder;(4) receive a selected vehicle class inputted by the policyholder viathe user device, wherein the selected vehicle class is available forrent at the at least one rental vendor location; (5) calculate, apolicyholder cost for the selected vehicle class based upon thepolicyholder insurance data, the selected vehicle class, and the rentalvehicle data for the at least one rental vendor; (6) display, to thepolicyholder, a cost summary including the policyholder cost andinformation as to the calculation of the policyholder cost; and/or (7)receive, from the policyholder, confirmation of a rental reservationrequest of the selected vehicle class at the at least one rental vendorlocation.

A further enhancement may be where the policyholder insurance dataincludes rental vehicle provisions of the automobile insurance policy asof the date and time the claim identifier is generated (e.g., firstnotice of loss filed).

A further enhancement may be where the computer system provides adelivery option to the policyholder. The delivery option may enable thepolicyholder to schedule either a vehicle pick-up at the at least onerental vendor location or a vehicle delivery, by the at least one rentalvendor location, to the policyholder.

A further enhancement may be where the computer system verifies that thepolicyholder is eligible to receive an insurance replacement rental bydetermining that a pay code for the initial loss claim submission hasbeen generated and stored within the memory. Another enhancement may bewhere the computer system transmits the rental reservation request tothe at least one vendor location. The company system may also transmitat least some of the policyholder insurance data to the at least onevendor location.

A further embodiment may be where the computer system updates a claimfile of the policyholder to include the rental reservation request. Theclaim file may contain information related to the initial loss claimsubmission. A further embodiment may be where the computer systemgenerates a file note for a claims handler. The file note may includethe rental reservation request. A still further embodiment may be wherethe computer system outputs a rental vehicle recommendation (e.g., bestrental option) for the policyholder based on the calculation.

A further embodiment may be where the subset of rental vehicle data isbased at least on a geolocation input by the policyholder. The subset ofrental vehicle data may include at least one rental vendor applicable tothe policyholder and a subset of vehicle classes available for rent bythe at least one rental vendor. Another embodiment may be where thecomputer system (1) retrieves, repair facility information of at leastone repair facility associated with the policyholder from an insuranceprovider database; and (2) displays, to the policyholder, availablerental vendor locations near the at least one repair facility.

Machine Learning & Other Matters

The computer-implemented methods discussed herein may includeadditional, less, or alternate actions, including those discussedelsewhere herein. The methods may be implemented via one or more localor remote processors, transceivers, servers, and/or sensors (such asprocessors, transceivers, servers, and/or sensors mounted on vehicles ormobile devices, or associated with smart infrastructure or remoteservers), and/or via computer-executable instructions stored on anon-transitory computer-readable media or medium.

Additionally, the computer systems discussed herein may includeadditional, less, or alternate functionality, including that discussedelsewhere herein. The computer systems discussed herein may include orbe implemented via computer-executable instructions stored on anon-transitory computer-readable media or medium.

A processor or a processing element may be trained using supervised orunsupervised machine learning, and the machine learning program mayemploy a neural network, which may be a convolutional neural network, adeep learning neural network, or a combined learning module or programthat learns in two or more fields or areas of interest. Machine learningmay involve identifying and recognizing patterns in existing data inorder to facilitate making predictions for subsequent data. Models maybe created based upon example inputs in order to make valid and reliablepredictions for novel inputs.

Additionally or alternatively, the machine learning programs may betrained by inputting sample data sets or certain data into the programs,such as images, object statistics and information, historical estimates,and/or actual repair costs. The machine learning programs may utilizedeep learning algorithms that may be primarily focused on patternrecognition, and may be trained after processing multiple examples. Themachine learning programs may include Bayesian program learning (BPL),voice recognition and synthesis, image or object recognition, opticalcharacter recognition, and/or natural language processing—eitherindividually or in combination. The machine learning programs may alsoinclude natural language processing, semantic analysis, automaticreasoning, and/or machine learning.

In supervised machine learning, a processing element may be providedwith example inputs and their associated outputs, and may seek todiscover a general rule that maps inputs to outputs, so that whensubsequent novel inputs are provided the processing element may, basedupon the discovered rule, accurately predict the correct output. Inunsupervised machine learning, the processing element may be required tofind its own structure in unlabeled example inputs. In one embodiment,machine learning techniques may be used to extract data about theobject, vehicle, user, damage, needed repairs, costs and/or incidentfrom vehicle data, insurance policies, geolocation data, image data,and/or other data.

Based upon these analyses, the processing element may learn how toidentify characteristics and patterns that may then be applied toanalyzing image data, model data, and/or other data. For example, theprocessing element may learn, with the user's permission or affirmativeconsent, to identify the type of incident that occurred based uponimages of the resulting damage. The processing element may also learnhow to identify damage that may not be readily visible based upon thereceived image data.

ADDITIONAL CONSIDERATIONS

As will be appreciated based upon the foregoing specification, theabove-described embodiments of the disclosure may be implemented usingcomputer programming or engineering techniques including computersoftware, firmware, hardware or any combination or subset thereof. Anysuch resulting program, having computer-readable code means, may beembodied or provided within one or more computer-readable media, therebymaking a computer program product, i.e., an article of manufacture,according to the discussed embodiments of the disclosure. Thecomputer-readable media may be, for example, but is not limited to, afixed (hard) drive, diskette, optical disk, magnetic tape, semiconductormemory such as read-only memory (ROM), and/or any transmitting/receivingmedium, such as the Internet or other communication network or link. Thearticle of manufacture containing the computer code may be made and/orused by executing the code directly from one medium, by copying the codefrom one medium to another medium, or by transmitting the code over anetwork.

These computer programs (also known as programs, software, softwareapplications, “apps”, or code) include machine instructions for aprogrammable processor, and can be implemented in a high-levelprocedural and/or object-oriented programming language, and/or inassembly/machine language. As used herein, the terms “machine-readablemedium” “computer-readable medium” refers to any computer programproduct, apparatus and/or device (e.g., magnetic discs, optical disks,memory, Programmable Logic Devices (PLDs)) used to provide machineinstructions and/or data to a programmable processor, including amachine-readable medium that receives machine instructions as amachine-readable signal. The “machine-readable medium” and“computer-readable medium,” however, do not include transitory signals.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

As used herein, a processor may include any programmable systemincluding systems using micro-controllers, reduced instruction setcircuits (RISC), application specific integrated circuits (ASICs), logiccircuits, and any other circuit or processor capable of executing thefunctions described herein. The above examples are example only, and arethus not intended to limit in any way the definition and/or meaning ofthe term “processor.”

As used herein, the terms “software” and “firmware” are interchangeable,and include any computer program stored in memory for execution by aprocessor, including RAM memory, ROM memory, EPROM memory, EEPROMmemory, and non-volatile RAM (NVRAM) memory. The above memory types areexample only, and are thus not limiting as to the types of memory usablefor storage of a computer program.

In one embodiment, a computer program is provided, and the program isembodied on a computer readable medium. In an exemplary embodiment, thesystem is executed on a single computer system, without requiring aconnection to a sever computer. In a further embodiment, the system isbeing run in a Windows® environment (Windows is a registered trademarkof Microsoft Corporation, Redmond, Wash.). In yet another embodiment,the system is run on a mainframe environment and a UNIX® serverenvironment (UNIX is a registered trademark of X/Open Company Limitedlocated in Reading, Berkshire, United Kingdom). The application isflexible and designed to run in various different environments withoutcompromising any major functionality.

In some embodiments, the system includes multiple components distributedamong a plurality of computing devices. One or more components may be inthe form of computer-executable instructions embodied in acomputer-readable medium. The systems and processes are not limited tothe specific embodiments described herein. In addition, components ofeach system and each process can be practiced independent and separatefrom other components and processes described herein. Each component andprocess can also be used in combination with other assembly packages andprocesses. The present embodiments may enhance the functionality andfunctioning of computers and/or computer systems.

As used herein, an element or step recited in the singular and precededby the word “a” or “an” should be understood as not excluding pluralelements or steps, unless such exclusion is explicitly recited.Furthermore, references to “example embodiment” or “one embodiment” ofthe present disclosure are not intended to be interpreted as excludingthe existence of additional embodiments that also incorporate therecited features.

The patent claims at the end of this document are not intended to beconstrued under 35 U.S.C. § 112(f) unless traditionalmeans-plus-function language is expressly recited, such as “means for”or “step for” language being expressly recited in the claim(s).

This written description uses examples to disclose the disclosure,including the best mode, and also to enable any person skilled in theart to practice the disclosure, including making and using any devicesor systems and performing any incorporated methods. The patentable scopeof the disclosure is defined by the claims, and may include otherexamples that occur to those skilled in the art. Such other examples areintended to be within the scope of the claims if they have structuralelements that do not differ from the literal language of the claims, orif they include equivalent structural elements with insubstantialdifferences from the literal language of the claims.

We claim:
 1. A rental self-service (“RSS”) computer system comprising aprocessor in communication with a memory, the processor programmed to:verify, in response to an initial loss claim filed by a policyholder,that the policyholder is eligible to receive an insurance replacementrental by performing an eligibility check using a claim identifierassociated with the initial loss claim and a policyholder identifierassociated with the policyholder; in response to the policyholder beingverified as eligible, generate a customized link including arepresentation of the claim identifier and the policyholder identifier;transmit the customized link to a user device associated with thepolicyholder; in response to selection of the customized link at theuser device, receive, from the user device, an access request for accessof a rental self-service portal, the access request identifying thecustomized link selected by the policyholder; retrieve, from a database,using the representation of the claim identifier and the policyholderidentifier extracted from the customized link identified in the accessrequest, policyholder data; pre-populate a portion of a searchableinterface of the rental self-service portal using the retrievedpolicyholder data, for display on the user device; in response toreceiving rental vehicle search input into the searchable interface,retrieve, via a plurality of Application Interface Programming (API)calls to a respective plurality of vehicle rental vendor devices, rentalvehicle data that satisfies the rental vehicle search input; cause therental vehicle data to be displayed on the user device to enable thepolicyholder to view available rental options and select a vehicle classavailable for rent; calculate a policyholder cost for renting a selectedvehicle class based upon the policyholder data and a correspondingvehicle rental quote for the selected vehicle class, the policyholdercost including a difference between a covered rental amount indicated inthe retrieved policyholder data and a rental cost indicated in thevehicle rental quote; and cause to be displayed on the user device (i)the calculated policyholder cost and (ii) an option to confirm therental reservation.
 2. The RSS computer system of claim 1, wherein topre-populate the portion of the searchable interface, the processor isfurther programmed to retrieve and display, in one or more correspondingsearch input fields, rental coverage details associated with aninsurance policy of the policyholder and a primary rental vendor at ageographical location associated with the policyholder.
 3. The RSScomputer system of claim 1, wherein the processor is further programmedto cause display of the pre-populated searchable interface on the userdevice, the pre-populated searchable interface including input fieldsfor receiving rental vehicle search input from the policyholderincluding one or more of: a geographical location relative to a currentlocation of the policyholder, a geographical location relative to arepair facility, the vehicle class, a vehicle make, a vehicle model, ora vehicle availability.
 4. The RSS computer system of claim 1, whereinthe processor is further programmed to, when the policyholder cost isgreater than a threshold amount: identify a non-selected vehicle class;determine that selection of the non-selected vehicle class would reducethe policyholder cost below the threshold amount; and cause to bedisplayed on the user device (iii) a recommendation that the user selectthe non-selected vehicle class to reduce the policyholder cost.
 5. TheRSS computer system of claim 1, wherein the processor is furtherprogrammed to: retrieve, as part of the policyholder data, a location ofa designated repair facility of the policyholder; and upon confirmationof the rental reservation, initiate delivery of a vehicle in theselected vehicle class to the designated repair facility.
 6. The RSScomputer system of claim 1, wherein performing the eligibility checkincludes applying a plurality of eligibility rules to information in theinitial loss claim.
 7. The RSS computer system of claim 1, wherein theprocessor is further programmed to: receive, from the user device, theinitial loss claim via a software application executed on the userdevice; and cause display of the searchable interface within a userinterface of the same software application executed on the user device.8. The RSS computer system of claim 1, wherein the processor is furtherprogrammed to transmit the rental reservation and at least some of thepolicyholder data to a selected vendor location.
 9. Acomputer-implemented method for enabling a policyholder to initiate areplacement rental reservation after submission of an initial lossclaim, the method implemented on a rental self-service (“RSS”) computingdevice including at least one processor in communication with at leastone memory device, the method comprising: verifying, in response to aninitial loss claim filed by a policyholder, that the policyholder iseligible to receive an insurance replacement rental by performing aneligibility check using a claim identifier associated with the initialloss claim and a policyholder identifier associated with thepolicyholder; in response to the policyholder being verified aseligible, generating a customized link including a representation of theclaim identifier and the policyholder identifier; transmitting thecustomized link to a user device associated with the policyholder; inresponse to selection of the customized link at the user device,receiving, from the user device, an access request for access of arental self-service portal, the access request identifying thecustomized link selected by the policyholder; retrieving, from adatabase, using the representation of the claim identifier and thepolicyholder identifier extracted from the customized link identified inthe access request, policyholder data; pre-populating a portion of asearchable interface of the rental self-service portal using theretrieved policyholder data, for display on the user device; in responseto receiving rental vehicle search input into the searchable interface,retrieving, via a plurality of Application Interface Programming (API)calls to a respective plurality of vehicle rental vendor devices, rentalvehicle data that satisfies the rental vehicle search input; causing therental vehicle data to be displayed on the user device to enable thepolicyholder to view available rental options and select a vehicle classavailable for rent; calculating a policyholder cost for renting aselected vehicle class based upon the policyholder data and acorresponding vehicle rental quote for the selected vehicle class, thepolicyholder cost including a difference between a covered rental amountindicated in the retrieved policyholder data and a rental cost indicatedin the vehicle rental quote; and causing to be displayed on the userdevice (i) the calculated policyholder cost and (ii) an option toconfirm the rental reservation.
 10. The method of claim 9, whereinpre-populating the portion of the searchable interface comprisesretrieving and displaying, in one or more corresponding search inputfields, rental coverage details associated with an insurance policy ofthe policyholder and a primary rental vendor at a geographical locationassociated with the policyholder.
 11. The method of claim 9, furthercomprising causing display of the pre-populated searchable interface onthe user device, the pre-populated searchable interface including inputfields for receiving rental vehicle search input from the policyholderincluding one or more of: a geographical location relative to a currentlocation of the policyholder, a geographical location relative to arepair facility, the vehicle class, a vehicle make, a vehicle model, ora vehicle availability.
 12. The method of claim 9, further comprising,when the policyholder cost is greater than a threshold amount:identifying a non-selected vehicle class; determining that selection ofthe non-selected vehicle class would reduce the policyholder cost belowthe threshold amount; and causing to be displayed on the user device(iii) a recommendation that the user select the non-selected vehicleclass to reduce the policyholder cost.
 13. The method of claim 9,further comprising: retrieving, as part of the policyholder data, alocation of a designated repair facility of the policyholder; and uponconfirmation of the rental reservation, initiating delivery of a vehiclein the selected vehicle class to the designated repair facility.
 14. Themethod of claim 9, wherein performing the eligibility check comprisingapplying a plurality of eligibility rules to information in the initialloss claim.
 15. The method of claim 9, further comprising: receiving,from the user device, the initial loss claim via a software applicationexecuted on the user device; and causing display of the searchableinterface within a user interface of the same software applicationexecuted on the user device.
 16. The method of claim 9, furthercomprising transmitting the rental reservation and at least some of thepolicyholder data to a selected vendor location.
 17. A non-transitorycomputer-readable storage media having computer-executable instructionsembodied thereon for enabling a policyholder to initiate a replacementrental reservation, wherein when executed by at least one processor ofan RSS computing device, the computer-executable instructions cause theat least one processor to: verify, in response to an initial loss claimfiled by a policyholder, that the policyholder is eligible to receive aninsurance replacement rental by performing an eligibility check using aclaim identifier associated with the initial loss claim and apolicyholder identifier associated with the policyholder; in response tothe policyholder being verified as eligible, generate a customized linkincluding a representation of the claim identifier and the policyholderidentifier; transmit the customized link to a user device associatedwith the policyholder; in response to selection of the customized linkat the user device, receive, from the user device, an access request foraccess of a rental self-service portal, the access request identifyingthe customized link selected by the policyholder; retrieve, from adatabase, using the representation of the claim identifier and thepolicyholder identifier extracted from the customized link identified inthe access request, policyholder data; pre-populate a portion of asearchable interface of the rental self-service portal using theretrieved policyholder data, for display on the user device; in responseto receiving rental vehicle search input into the searchable interface,retrieve, via a plurality of Application Interface Programming (API)calls to a respective plurality of vehicle rental vendor devices, rentalvehicle data that satisfies the rental vehicle search input; cause therental vehicle data to be displayed on the user device to enable thepolicyholder to view available rental options and select a vehicle classavailable for rent; calculate a policyholder cost for renting a selectedvehicle class based upon the policyholder data and a correspondingvehicle rental quote for the selected vehicle class, the policyholdercost including a difference between a covered rental amount indicated inthe retrieved policyholder data and a rental cost indicated in thevehicle rental quote; and cause to be displayed on the user device (i)the calculated policyholder cost and (ii) an option to confirm therental reservation.
 18. The non-transitory computer-readable storagemedia of claim 17, wherein the computer-executable instructions furthercause the at least one processor to, when the policyholder cost isgreater than a threshold amount: identify a non-selected vehicle class;determine that selection of the non-selected vehicle class would reducethe policyholder cost below the threshold amount; and cause to bedisplayed on the user device (iii) a recommendation that the user selectthe non-selected vehicle class to reduce the policyholder cost.